Update Yarn to v1.22.21 #1121
Open
Update Yarn to v1.22.21 #1121
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/yarn-1.22.x
branch
from
69f3ed0
to
d1b082f
Compare
renovate
bot
force-pushed
the
renovate/yarn-1.22.x
branch
from
d1b082f
to
bb37abf
Compare
renovate
bot
force-pushed
the
renovate/yarn-1.22.x
branch
from
bb37abf
to
c91f64d
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.22.19->1.22.21Release Notes
yarnpkg/yarn (yarn)
v1.22.21Compare Source
Fixes an issue in the v1.22.20 when calling Yarn from a project subfolder, outside of a Corepack context.
Added a
SKIP_YARN_COREPACK_CHECKenvironment variable to skip the Corepack check.v1.22.20Compare Source
Important: Punycode is now embed within the bundle, as it has been deprecated by Node.js and will be removed in a future version.
A message will be displayed when Yarn 1.22 notices that the local project has a package.json file referencing a non-1.x Yarn release via the
packageManagerfield. The message will explain that the project is intended to be used with Corepack.The
yarn-error.logfiles won't be generated anymore, as we don't process non-critical 1.x bug reports (we however process all bugs reported on https://github.com/yarnpkg/berry; we just released the 4.0.2 release there).The
yarn set version x.y.zcommand will now install the exactx.y.zversion (prior to this change it used to first install the latest version, and only in a second step would it downgrade tox.y.z; this was causing issues when we bump the minimal Node.js version we support, as runningyarn set version 3.6.4wouldn't work on Node 16).Prevents crashes when reading from an empty
.yarnrc.ymlfile.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.